Skip to content

Release alert microsoft.alerts management preview/2025 05 25 preview (2)#35970

Merged
emi273 merged 58 commits intoAzure:mainfrom
emi273:release-alert-Microsoft.AlertsManagement-preview/2025_05_25_preview
Jul 31, 2025
Merged

Release alert microsoft.alerts management preview/2025 05 25 preview (2)#35970
emi273 merged 58 commits intoAzure:mainfrom
emi273:release-alert-Microsoft.AlertsManagement-preview/2025_05_25_preview

Conversation

@emi273
Copy link
Copy Markdown
Contributor

@emi273 emi273 commented Jul 17, 2025 •
edited
Loading

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
  • A release plan has been created. If not, please create one as it will help guide you through the REST API and SDK creation process.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.
  • For guidance on SDK breaking change review, refer to https://aka.ms/ci-fix.

Emmy Filtser added 4 commits July 17, 2025 10:11
Copy files from stable/2019-03-01
d3fa29b 
Copied the files in a separate commit.
This allows reviewers to easily diff subsequent changes against the previous spec.
Update version to preview/2025-05-25-preview
5ece950 
Updated the API version from stable/2019-03-01 to preview/2025-05-25-preview.
Added tag for 2025-05-25-preview in readme file
3d9c861
add changes 2025
5aa54c3
@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app bot commented Jul 17, 2025 •
edited
Loading

Next Steps to Merge

⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app bot commented Jul 17, 2025 •
edited
Loading

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Jul 17, 2025
@AzureRestAPISpecReview AzureRestAPISpecReview added ARMReview resource-manager SuppressionReviewRequired WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 17, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Jul 17, 2025 •
edited
Loading

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.AlertsManagement
Go sdk/resourcemanager/alertsmanagement/armalertsmanagement
Python azure-mgmt-alertsmanagement

@emi273 emi273 added ARMChangesRequested Approved-Avocado PublishToCustomers Acknowledgement the changes will be published to Azure customers. labels Jul 17, 2025
@openapi-pipeline-app openapi-pipeline-app bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 17, 2025
@yogev2125 yogev2125 assigned yogev2125 and unassigned yogev2125 Jul 17, 2025
@yogev2125 yogev2125 self-requested a review July 17, 2025 13:38
@emi273
Copy link
Copy Markdown
Contributor Author

emi273 commented Jul 28, 2025

/azp run

@azure-pipelines
Copy link
Copy Markdown

azure-pipelines bot commented Jul 28, 2025

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@gary-x-li gary-x-li added Approved-Suppression ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review labels Jul 28, 2025
Yogev Kleinberger and others added 2 commits July 30, 2025 09:16
@emi273
Copy link
Copy Markdown
Contributor Author

emi273 commented Jul 31, 2025

/azp run

@azure-pipelines
Copy link
Copy Markdown

azure-pipelines bot commented Jul 31, 2025

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@emi273
Copy link
Copy Markdown
Contributor Author

emi273 commented Jul 31, 2025

/azp run

@azure-pipelines
Copy link
Copy Markdown

azure-pipelines bot commented Jul 31, 2025

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@emi273
Copy link
Copy Markdown
Contributor Author

emi273 commented Jul 31, 2025

/azp run

@azure-pipelines
Copy link
Copy Markdown

azure-pipelines bot commented Jul 31, 2025

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gary-x-li gary-x-li gary-x-li approved these changes

@Avivskie Avivskie Avivskie approved these changes

+2 more reviewers

@yogev2125 yogev2125 yogev2125 approved these changes

@TamRuas TamRuas TamRuas approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

Alerts Management Approved-Avocado Approved-Suppression ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review BreakingChange-Approved-Previously Changes were reviewed and approved in a previous PR BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager SuppressionReviewRequired

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@emi273 @gary-x-li @Avivskie @TamRuas @yogev2125 @AzureRestAPISpecReview